Employing code overlays to facilitate software development

ABSTRACT

In one embodiment, a method for editing and testing computer programming code is provided. The method includes receiving a first file comprising computer programming code, and a first code overlay comprising one or more modifications to be applied to the computer programming code of the first file. The method further includes determining a first location within the computer programming code of the first file, at which to apply the first code overlay. The method further includes generating a second file comprising uncompiled composite computer programming code, the uncompiled composite computer programming code comprising the computer programming code of the first file modified by the one or more modifications applied at the first location. The method further includes testing the uncompiled composite computer programming code of the second file.

BACKGROUND OF THE INVENTION

The present invention relates generally to the field of debuggingsoftware applications, and more particularly to employing code overlaysto apply and remove code from within a software application.

Debugging applications typically involves executing applications in asimulated run-time environment. Debugging an application allows adeveloper to identify errors in the application's code and correct them.Debugging of applications can be done in numerous ways, including forexample, in a development environment used to develop the applicationcode or alternatively in a debugging component associated with a webbrowser.

An application is defined by application code. The application code maydiffer depending on the type of device, or the runtime environment inwhich the application is executed. For example, source code or objectcode may be written in any combination of one or more programminglanguages, including an object oriented programming language, such asSmalltalk, C++ or the like, and conventional procedural programminglanguages, such as the “C” programming language or similar programminglanguages. Alternatively, the application code may be expressed using amark-up language, such as hypertext mark-up language (HTML) or a scriptlanguage. In addition to the application code, the application may alsoinclude dynamically generated code, which is generated by theapplication code during execution of the application. Depending on theprogramming language that is used to create a software application, theapplication code may need to be compiled into a machine language versionof the application. Other programming languages are capable of beingexecuted via a software interpreter. Interpreters and compilers are notmutually exclusive. An interpreter may execute a program by parsing thesource code and performing its behavior directly, by translating sourcecode into some efficient intermediate representation and immediatelyexecuting the representation, or by explicitly executing stored,precompiled code made by a compiler that is part of the interpretersystem.

SUMMARY

According to one embodiment of the present invention, a method forediting and testing computer programming code is provided, the methodcomprising: receiving, by one or more computer processors, a first filecomprising computer programming code; receiving, by one or more computerprocessors, a first code overlay comprising one or more modifications tobe applied to the computer programming code of the first file;determining, by the one or more computer processors, a first locationwithin the computer programming code of the first file, at which toapply the first code overlay; generating, by one or more processors, asecond file comprising uncompiled composite computer programming code,the uncompiled composite computer programming code comprising thecomputer programming code of the first file modified by the one or moremodifications applied at the first location; and testing, by one or morecomputer processors, the uncompiled composite computer programming codeof the second file.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a distributed data processing environment, inaccordance with an embodiment of the present invention.

FIG. 2 depicts a flowchart of operational steps of a code overlaycreation program, in accordance with an embodiment of the presentinvention.

FIG. 3 depicts a flowchart of operational steps of a code overlayintegration program, in accordance with an embodiment of the presentinvention.

FIG. 4a depicts an illustrative example of a source code snippet, inaccordance with an embodiment of the present invention.

FIG. 4b depicts an illustrative example of results of two code overlaysapplied to the source code snippet of FIG. 4a to generate a snippet ofcomposite code, in accordance with an embodiment of the presentinvention.

FIG. 4c depicts an illustrative example of creating a code overlaycomprised of a descriptive comment from text added at multiple locationsin the source code snippet of FIG. 4a , in accordance with an embodimentof the present invention

FIG. 5 is a block diagram of components of a computer, in accordancewith an embodiment of the present invention.

DETAILED DESCRIPTION

Embodiments of the present invention recognize that debugging computerprogramming code and fixing defects are necessary steps in the softwaredevelopment cycle. For example, programmers can use temporary portionsof computer programming code to: output (e.g., print out) debugstatements, debug error messages, force specific paths in code, assignpreset sources of information (e.g., variables, director paths, filenames, tables, links to other software modules or applications, etc.)and then undo these changes (e.g., temporary portions of code). Somesoftware languages provide options to incorporate logical statementsthat remove the debug code from the source code allowing the conditionalcompiling of a program. Embodiments of the present invention recognizethat utilizing conditional compiling of a program has drawbacks. Some ofthese drawbacks include that the “undo” change option may be complicatedwhen some changes are to be preserved, and “undo” typically does notallow changes to be preserved for future use. Other drawbacks toconditional compilation for managing debug options include: conditionalflags need to be managed to control which options are incorporated andwhich options are excluded from the compiled program, creatingstatements that facilitate conditional compiling adds complexity to thesource code and forms sources of errors when improperly structured, andimproperly structured conditional compilation statements may incorporateunwanted debug code within the compiled program.

Embodiments of the present invention provide users a method, via codeoverlays, to individually or collaboratively test and debug softwareprograms without adding extraneous programming instruction to a sourcecode file. Embodiments of the present invention apply code overlay tosource code to generate composite code, leaving the source codeunaltered (e.g., in an original state). Embodiments of the presentinvention provide the capability to save the composite code in variousconfigurations (e.g., as composite code, as a testing/debugging scheme,and/or as a new version of source code). For example, code overlays canbe comprised of one or more lines of computer programming code that:output error information produced by executing the source code, outputinformation produced by portions of the source code, specify inputinformation employed by the source code, dictate execution paths in thecomposite computer programming code of the second file, and/or providedocumentation information. In addition, a code overlay may also includetext that is informational as opposed to executable code, and some,none, or all of the informational text can be applied to the sourcecode. For example, information embedded within a code overlay orassociated with a code overlay may include: location information (e.g.,source code line number, source code offset/index value), the name of acode overlay, the directory location of a code overlay, a permissionlevel, the author (e.g., programmer) of the code overlay, source codefile employing the code overlay, etc. In various embodiments of thepresent invention, some operating systems may provide Diff/Patch (notshown) mechanisms (e.g., utilities, functions) that provide a method toidentify code overlays written within a file of modified source code andanother method to revert the modified source code to the original sourcecode (e.g., original state).

In some embodiments of the present invention, debugging code may beinitially written in the source code to be subsequently converted to acode overlay, stored, and disassociated from the source code when notneeded, leaving the source code unaltered. In these embodiments, a codeoverlay is associated with a specific location within the source code.Further embodiments facilitate the creation of a library of codeoverlays that contain code overlays that may be selected by a user to beapplied to other locations within a source code file or the creation ofconfigurations (e.g., schemes) to test and debug other source codefiles. For example, by incorporating lists, tables, cross-references,meta-data, and script functions, embodiments of the present inventionpermit: code overlays to be shared between users, the creation ofmultiple testing and debugging schemes for a source code file, testingand debugging results to be stored and associated with a testing anddebugging scheme, and applying testing and debugging schemes created forone source code file to be adapted for use with a different source codefile. Other embodiments of the present invention provide capabilitiesthat permit code overlays to be created off-line (e.g., outside of thesource code, using a different editing program, etc.), stored in alibrary, and selected and applied to a file of source code as needed.

Additional embodiments of the present invention provide additionalfunctionality that responds to information embedded in a code overlay.For example, a code overlay may contain one or more functional lines oftext that are comprised of a character or combinations of characterswhose syntax defines various functions and methods to process commands,variables, text, and code that effects the behavior of a code overlay,as opposed to incorporation within the source code. Examples of theeffects of syntax commands within a functional line of text within acode overlay are syntax commands to: define an insertion point, generatepseudo-code, define number of repetitions of inserted code, andchain/combine actions. In one embodiment, a code overlay may have thecapability to identify lines of source code located relative to theapplication location of the code overlay (e.g., insertion point, offsetvalue, line number, etc.) and execute one or more actions defined withinthe code overlay on the identified lines of source code. For example, afirst portion of a code overlay may comment-out lines of source codeprior to applying the programming code comprising a subsequent portionof the code overlay. In another embodiment, a code overlay converts theidentified lines of source code to another code overlay, replaces theidentified lines of source code with some or all of the code comprisingthe code overlay, and embeds information within the other code overlaythat facilitates an undo option once the testing and debug of the sourcecode is complete. In further embodiments, pseudo-code within a codeoverlay may produce lines of text which are subsequently applied togenerate the composite code, or the pseudo-code may generate additionalfunctional lines within the code overlay, which affects the generationof composite code.

The descriptions of the various scenarios, instances, and examplesrelated to the present invention are presented for purposes ofillustration but are not intended to be exhaustive or limited to theembodiments disclosed. Similarly, the descriptions of the variouslayouts, syntax, functions, and capabilities associated with codeoverlays related to the present invention are presented for purposes ofillustration but are not intended to be exhaustive or limited to theembodiments disclosed. The descriptions of the various scenarios,instances, and examples related to the present invention utilize theconvention that an insertion point, or an offset value associated withapplying information from a code overlay to source code, occurs below aline of code associated with the insertion point or the offset value.Deletion of source code, or replacement of source code, occurs at theline of code associated with the insertion point or the offset value. Ingeneral, any desired convention can be used.

The present invention will now be described in detail with reference tothe Figures. FIG. 1 is a functional block diagram illustratingdistributed data processing environment 100 in an embodiment, inaccordance with the present invention. An embodiment of distributed dataprocessing environment 100 includes server 102, client device 120, andclient device 130 interconnected over network 110. Many modifications tothe depicted environment may be made by those skilled in the art withoutdeparting from the scope of the invention as recited by the claims.

Server 102, client device 120, and client device 130 may be laptopcomputers, tablet computers, netbook computers, personal computers (PC),desktop computers, personal digital assistants (PDA), smart phones, orany programmable computer systems known in the art. In certainembodiments, server 102, client device 120, and client device 130represent computer systems utilizing clustered computers and components(e.g., database server computers, application server computers, etc.)that act as pools of seamless resources when accessed through network110, as is common in data centers and with cloud-computing applications.In general, server 102, client device 120, and client device 130 arerepresentative of any programmable electronic devices or combination ofprogrammable electronic devices capable of executing machine readableprogram instructions, as depicted and described in further detail withrespect to FIG. 5.

Server 102 includes file storage 104, source code 106, composite code107, software editing program 108, code overlay creation program 200,and code overlay integration program 300. Server 102 can also includevarious other programs that are not shown for illustrative purposes(e.g., text editor, software debug utility, etc.). In some embodiments,server 102 may contain a database program that maintains libraries ofcode overlays (not shown), maintains listings of code overlays andassociated offsets for various software applications (not shown), andcontrols access/permission levels of code overlays (e.g., shared,private, secured, read-only, update, delete, etc.). In some embodiments,software editing program 108, code overlay creation program 200, codeoverlay integration program 300, a database program, and other functions(not shown) are bundled together as an integrated developmentenvironment (IDE) (e.g., software suite). In other embodiments, the IDE(not shown) is a separate software suite. The IDE may include softwareediting program 108 and a dedicated debugger program (not shown).

In one embodiment, file storage 104 contains one or more databases andlists of code overlays and associated information. For example, filestorage 104 may contain: libraries of code overlays (e.g., code overlayfile names, code overlay descriptions, revision levels, etc.) maintainedby a database program, listings of code overlays and associatedoffsets/indexes for various software applications, informationcontrolling the access/permission levels of code overlays (e.g., shared,private, secured, read-only, update, delete, etc.), and tables crossreferencing various testing schemes (e.g., applied code overlays) usedfor testing source code 106, and the results of utilizing the varioustesting schemes. File storage 104 may also contain the one or moreresultant files of testing and/or debug activity which include: errorcodes, error messages, variables, exception handling, dictated executionpaths, lists, database tables, etc. In some instances, a user of clientdevice 120 may review the resultant files in-situ (e.g., while executingcomposite code 107) and compare the obtained results with the resultsexpected from executing source code 106. In other instances, a user ofserver 102 may review the files resulting from the execution ofcomposite code 107 and compare the obtained results with the resultsexpected from executing source code 106. In another embodiment, filestorage 104 contains individual instances of code overlays. For example,each instance of a code overlay, contained within file storage 104,contains one defined offset/index identifying the location where thatinstance of a code overlay is applied to source code 106. In someembodiments, file storage 104 contains composite computer programmingcode generated by code overlay integration program 300.

Source code 106 is comprised of computer programming code that includesexecutable lines of code and lines of code that are comments.

Composite code 107 is comprised of source code 106 and one or more codeoverlays. In one embodiment, composite code 107 contains unmodifiedsource code 106 and one or more code overlays applied at dictatedlocations within source code 106. In one scenario, offset values (e.g.,index, number associated with a line of source code) that dictate thelocations of the one or more code overlays are defined within each ofthe one or more code overlays. In some scenarios, composite code 107 iscomprised of code overlays that may be applied at more than one locationwithin source code 106. For example, a code overlay may contain threeoffset values associated with source code 106. The code overlay isapplied at each of the identified locations respectively associated withan offset value.

In one embodiment, software editing program 108 executes on server 102and is accessed by client device 120 and client device 130 via network110. Software editing program 108 is utilized by a user of client device120 and a user of client device 130 via UI 122 and UI 132, respectively.In another embodiment, a version of software editing program 108executes on client device 120 and client device 130, respectively (notshown), and uploads code overlays to server 102. In some embodiments,software editing program 108 provides a user of client device 120 thecapability to create a code overlay and the ability to define a locationwithin source code 106 where code overlay integration program 300 shouldapply the code overlay.

Code overlay creation program 200 produces code overlays. Code overlaycreation program 200 may execute concurrently with software editingprogram 108 and code overlay integration program 300. In one embodiment,code overlay creation program 200 receives one or more indications fromsoftware editing program 108 that a user converts a portion of sourcecode 106 to a code overlay. For example, code overlay creation program200 can remove a portion of source code 106 that is now a code overlayand determine a location where the code overlay initially existed. Inone scenario, code overlay creation program 200 defines an offset/indexvalue within the code overlay based on the location from where the codeoverlay was removed from source code 106. In another scenario, codeoverlay creation program 200 determines an offset/index that isassociated with the source code 106 and the code overlay and store theinformation in a table. In another embodiment, code overlay creationprogram 200 receives an indication from software editing program 108that a code overlay is applied to source code 106. The indicationreceived by code overlay creation program 200 includes the name of thecode overlay and a location (e.g., library) where the code overlay isstored.

In some embodiments, code overlay creation program 200 incorporates theoffset/index (e.g., line number) as a definition within the codeoverlay. In other embodiments, code overlay creation program 200generates an offset/index value for the code overlay and stores theoffset/index value within at least one of: one or more lists and one ormore tables of a database. Additionally, code overlay creation program200 determines whether source code 106 is modified while a user createsone or more code overlays. Code overlay creation program 200 resolvesconflicts attributed to modifications of source code 106 by at least oneof: determining whether the affected instance of source code 106 is on ashared location, determining whether a modification to source code 106occurs in a portion of code where a user is creating a code overlay,determining one or more user preferences, and determining one or moreIDE preferences. In further embodiments of the present invention, codeoverlay creation program 200 may compare two versions of source code 106to generate a file identifying the differences between the two versionsof source code 106. The file identifying the differences between the twoversions of source code 106 may be utilized to adjust offset values forcode overlays created by code overlay creation program 200 or utilizedby code overlay integration program 300.

Code overlay integration program 300 receives, generates, displays, andexecutes composite computer programming code based on applying one ormore code overlays to source code 106. In some embodiments, code overlayintegration program 300 receives a composite code configuration that mayapply additional code overlays, removes one or more code overlays, undochanges to a portion of source code 106 previously initiated by a codeoverlay, and performs additional executions of the composite code. Inone embodiment, code overlay integration program 300 applies codeoverlays in a sequential process and updates (e.g., applies biases) theoffset values of subsequent code overlays, as the effect of a currentcode overlay or previous code overlays is applied to source code 106 andas the lines of code comprising composite code 107 are renumbered. Inanother embodiment, code overlay integration program 300 receiveslocation information where each of the code overlays associated withsource code 106 are applied. Code overlay integration program 300 canapply the code overlays in a parallel process, renumbering the lines ofcode after the code overlays are applied. In one scenario, code overlayintegration program 300 applies the code overlays based on offset valuesdefined within individual code overlays. In another scenario, codeoverlay integration program 300 receives at least one of: one or morelists and one or more tables identifying the code overlays applied tosource code 106. The list or table of code overlays can include, forexample, line numbers or offset values identifying the locations wherecode overlay integration program 300 should apply each code overlay.

Additionally, code overlay integration program 300 can also facilitatethe testing and debugging of source code 106. In some embodiments, codeoverlay integration program 300 provides users one or more visualindications within composite code 107 that identify differences betweensource code 106 and code overlays. Code overlay integration program 300can also provide visual indications of additions and deletions to sourcecode 106 as incorporated within composite code 107, execution pathsaffected (e.g., dictated) by code within applied code overlays, andsources of data used for the execution of composite code 107. Examplesof visual indications provided by code overlay integration program 300may include: applying different colors to lines of source code, asopposed to colors applied to lines of code from a code overlay;depicting deleted lines of source code by use of a strikethrough fontand removal of line numbers; applying a bold font to portions of sourcecode modified by a code overlay; and enclosing in parentheses theoriginal portions of source code that were subsequently modified by acode overlay. In one scenario, code overlay integration program 300includes graphical (e.g., display) capabilities. In another scenario,code overlay integration program 300 utilizes the graphical (e.g.,display) capabilities of another program, such as software editingprogram 108, a software interpreter (not shown), or an IDE. In otherembodiments, code overlay integration program 300 executes compositecode 107. For example, the applied code overlays may: output errorinformation produced by executing composite code 107; output informationspecified by a code overlay; pause the execution of composite code;generate one or more handling exceptions; and store data and results foroff-line analysis, as dictated by a code overlay. In variousembodiments, code overlay integration program 300 receives an indicationfrom a user, via UI 122, that a version of composite code 107 is savedas a different source code 106 file. For example, a user may indicatethat some, none, or all of the code overlays and updates determined fromthe debugging activity of composite code 107 are saved as a differentversion of source code 106.

In other embodiments, code overlay integration program 300 resolvesconflicts attributed to modifications of source code 106 by determiningat least one of: whether the affected instance of source code 106 is ona shared location; whether a modification to source code 106 occurs in aportion of code where a user is creating a code overlay; an order ofprecedence (e.g., time-stamp, hierarchy, etc.) associated with themodifications to source code 106; or the application of a code overlay,one or more user preferences, and one or more IDE preferences. Infurther embodiments, code overlay integration program 300 may compensatefor a conflict by identifying a file that includes the differencesbetween two versions of source code 106 and may modify the applicationof one or more code overlays based on information included within thefile identifying the differences between two versions of source code106.

In one embodiment, client device 120, client device 130, and server 102communicate through network 110. Network 110 can be, for example, alocal area network (LAN), a telecommunications network, a wireless localarea network (WLAN), a wide area network (WAN), such as the Internet, orany combination of the previous, and can include wired, wireless, orfiber optic connections. In general, network 110 can be any combinationof connections and protocols that will support communications betweenclient device 120, client device 130, and server 102, in accordance withembodiments of the present invention. In another embodiment, network 110operates locally via wired, wireless, or optical connections and can beany combination of connections and protocols (e.g., near fieldcommunication (NFC), laser, infrared, etc.).

Client device 120 and client device 130, respectively, include userinterfaces (UI) 122 and 132, file storage 124 and 134, and each mayinclude a web browser application (not shown) and various other programs(not shown). Client device 120 and client device 130 may also includeone or more software editing programs (not shown). A software editingprogram may be a stand-alone software application, a function includedin a web browser, part of a software compiler/interpreter, or may resideon server 102 accessible via UI 122 or UI 132. A user of client device120 or client device 130 can interact with UI 122 or UI 132,respectively, via a singular device, such as a touch screen (e.g.,display) that performs both input to a graphical user interface (GUI)and as an output device (e.g., a display) presenting a plurality oficons associated with software applications or images depicting theexecuting software application. Optionally, a software application(e.g., a web browser, a software editing program, etc.) can generate UI122, operating within the GUI of client device 120, or generate UI 132,operating within the GUI of client device 130. UI 122 accepts input froma plurality of input/output (I/O) devices (not shown) including, but notlimited to, a tactile sensor interface (e.g., a touch screen, atouchpad) or a natural user interface (e.g., voice control unit, motioncapture device, etc.). An I/O device interfacing with UI 122 may beconnected to client device 120 which may operate utilizing wired (e.g.,USB port) or wireless network communications (e.g., infrared, NFC,etc.). For example, an I/O device may be a peripheral, such as akeyboard, a mouse, a trackball, and a click wheel that provide inputfrom a user.

FIG. 2 is a flowchart depicting operational steps for code overlaycreation program 200 executing on server 102.

In step 202, code overlay creation program 200 receives code overlaycontent and identifies source code incorporating code overlay. Thecontent of a code overlay may be of a singular type or a combination oftypes. The types of content that comprises a code overlay includeexecutable source code, documentation information, values for variables,references to specific data or files (e.g., directory paths, file names,databases, etc.), debugging, and temporary code that dictates the sourcecode to utilize specific paths. In one embodiment, code overlay creationprogram 200 receives a code overlay that is created off-line. Forexample, a code overlay may be created by a text editor, a softwareeditor, or may be copied from another source (e.g., a webpage, adocument, the source code of another program). In this embodiment, thecode overlay may not contain an offset or index value. In someembodiments, code overlay creation program 200 may permit a user to editthe syntax information that controls the code overlay.

In another embodiment, code overlay creation program 200 receives thecode overlay content from the source code that is debugged. In onescenario, code overlay content is created within source code 106, andsoftware editing program 108 supports code overlay creation program 200.In this scenario, code overlay creation program 200 sets a flag (e.g.,pointer value) associated with the location within the original sourcecode file where the code overlay was created. In another scenario, codeoverlay creation program 200 receives the code overlay content from textedited (e.g., cut) from the original source code file. Additionally,code overlay creation program 200 identifies the source code (i.e.,source code 106) incorporating a code overlay. For example, code overlaycreation program 200 identifies the file name and the directorystructure associated with source code 106 via software editing program108. The information identifying the source code may subsequently beassociated with the code overlay or as data within a list or table thatidentifies a code overlay with a specific source code file.

In step 206, code overlay creation program 200 determines an offset orindex associated with a code overlay and the content items within thecode overlay. The offset/index describe the location within source code106 where the code overlay is subsequently applied. In one embodiment,the offset/index associated with a code overlay is embedded within thecode overlay. In addition, code overlay creation program 200 tracks thenumber of lines of text associated with the received content of a codeoverlay or the flagged content associated with a code overlay. In onescenario, code overlay creation program 200 may determine that multipleinstances of a code overlay are associated with source code 106. Codeoverlay creation program 200 determines an offset/index value for eachoccurrence of a code overlay associated with editing/bugging source code106 and code overlay creation program 200. In another scenario, codeoverlay creation program 200 creates a code overlay for each occurrenceof the code overlay within the source code. Each code overlay maycontain one or more offset/index values. For example, if code overlaycreation program 200 determines that multiple instances of the same textoccur within a code overlay, code overlay creation program 200 maysummarize the text and associated offset/index values as a more conciseformat within the code overlay. In some embodiments, code overlaycreation program 200 updates the offset/index values of one or more codeoverlays based on modification to source code 106, the flagging ofadditional code overlay content, and/or the tracked number of lines oftext associated with code overlay content.

In another embodiment, code overlay creation program 200 interacts witha database program to store the offset/index values for code overlaysassociated with debugging source code 106 in one or more lists and/orone or more tables, as opposed to defining the offset/index valueswithin the code overlays. The structure of such embodiments facilitates,for example, the reuse of a code overlay, the sharing of a code overlay,and applying the code overlay to different composite code 107 testingand debug configurations (e.g., scheme01, scheme02, etc.).

Tables 1 and 2 are illustrative examples of embodiments of the presentinvention utilizing debugging schemes that apply multiple code overlaysat various offset location within source code 106. In this embodiment,for testing and debug files “Name.v01.scheme01.html” and“Name.v01.scheme02.html”, the syntax controls within a code overlay usethe instance fields of Tables 1 and 2 to identify the number of timesthat a code overlay is applied to source code 106 (e.g., Name.v01.html),and the offset value fields of Tables 1 and 2 as the insertion pointsfor the code overlay, respectively. In some scenarios, the value of afield is directly written within a line of syntax for a code overlay. Inother scenarios, the line of syntax incorporates a variable as part ofthe statement where the variable updates based on a scheme (e.g., debugconfiguration).

TABLE 1 Example code overlay list with offsets associated with testingand debug configuration file: Name.v01.scheme01.html d:\IDE\sourcecode\Name.v01.html Name Code Code Code Overlay.001.txt Overlay.002.txtOverlay.003.txt Directory location d:\libraries\ d:\libraries\d:\libraries\ overlays overlays overlays Instance Offset value Offsetvalue Offset value 1  5 15 25 2 30 — 40 3 — — 60

TABLE 2 Example code overlay list with offsets associated with testingand debug configuration file: Name.v01.scheme02.html d:\IDE\sourcecode\Name.v01.html Name Code Code Code Overlay.001.txt Overlay.003.txtOverlay.004.txt Directory location d:\libraries\ d:\libraries\d:\libraries\ overlays d:overlays overlays Instance Offset value Offsetvalue Offset value 1  5 25 76 2 30 40 — 3 — 60 —

In step 208, code overlay creation program 200 determines whether sourcecode 106 was modified while a code overlay was developed or whetheradditional code overlay content was flagged. In one embodiment, codeoverlay creation program 200 determines whether source code 106 wasmodified while developing a code overlay, and code overlay creationprogram 200 determines one or more offset/index values for the codeoverlay and associated code overlay content. For example, code overlaycreation program 200 compares the file attributes (e.g., file size, timestamp, etc.) of source code 106 stored in file storage 104 to the fileattributes of source code 106 identified in step 202. In anotherembodiment, code overlay creation program 200 determines whetheradditional code overlay content is flagged. In one scenario, codeoverlay creation program 200 determines that one or more lines of codeflagged as code overlay content were copied to another portion of sourcecode 106 utilizing software editing program 108. In another scenario,another one or more lines of source code 106 are flagged as content fora code overlay. In one instance, flagged content is associated with onecode overlay. In another instance, the flagged content is associatedwith a different code overlay generated by further modification tosource code 106, which triggers a loop back to step 206 (via yes branch;decision step 210). In some instances, code overlay creation program 200determines that portions of the flagged content are respectivelyassociated with the creation of two or more code overlays.

In decision step 210, in response to a determination that source code106 was modified (yes branch; decision step 210), code overlay creationprogram 200 resolves the conflict associated with different versions(e.g., files containing modifications) of source code 106 (step 214).

Having determined that additional code overlay content is flagged, instep 208, code overlay creation program 200 subsequently resolves theconflict associated with the additional flagged code overlay content(yes branch; decision step 210). In some embodiments, code overlaycreation program 200 determines that source code 106 was both modifiedand additional code overlay content was flagged (yes branch; decisionstep 210).

In step 214, code overlay creation program 200 resolves the conflictcaused by the modification of source code 106 while one or more codeoverlays were developed. In one embodiment, code overlay creationprogram 200 resolves the conflict between versions (e.g., copies ofsource code 106 that contain different modifications) of source code 106and uses the initial version of source code 106. In one scenario, codeoverlay creation program 200 resolves the modification conflictaffecting source code 106 by determining that code overlay creationprogram 200 and code overlay integration program 300 are operating onthe same version of source code 106. For example, a user of clientdevice 120 and a user of client device 130 may be separately debuggingrespectively developed portions of source code 106. Both users maymodify source code 106 while creating code overlays for their respectiveportions of source code 106. However, code overlay creation program 200determines that each user is executing different instances of codeoverlay creation program 200 and code overlay integration program 300,operating on separate copies of source code 106, so modifications tosource code 106 do not cause a conflict. In another scenario, codeoverlay creation program 200 determines that a user of client device 120and a user of client device 130 are collaboratively debugging portionsof source code 106 that were respectively developed. Code overlaycreation program 200 determines that no conflict occurs since themodification of portions of source code 106 of one user do not occur atthe locations of code overlays of the other user. In some scenarios,code overlay creation program 200 resolves the conflict between versionsof source code 106 by analyzing at least one of: one or more userpreferences and one or more software development preferences. Forexample, code overlay creation program 200 may determine that a softwaredevelopment preference dictates that a user downloads a copy of sourcecode 106 to local storage (e.g., file storage 124 on client device 120)and executes code overlay creation program 200 and code overlayintegration program 300 remotely, via UI 122 and network 110.

In another embodiment, code overlay creation program 200 resolvesconflict between a modified version of source code 106 and the initialversion of source code 106 and selects the modified version of sourcecode 106. For example, portions of source code 106 may be converted toone or more code overlays, and the code line values for the modifiedversion of source code 106 can be changed. These changes affect theoffset values of code overlays applied to the modified version of sourcecode 106.

In some embodiments, the stored version of source code 106 is notmodified. However, code overlay creation program 200 determines that aversion of source code 106 active in software editing program 108 ismodified by the creation of one or more additional code overlays orcontent assigned to one or more other code overlays. Code overlaycreation program 200 can determine that a conflict occurs based onnumbering changes associated with the code line values of the editedversion of source code 106. Code overlay creation program 200compensates offset values for one or more code overlays for the one ormore changes in code line numbering of source code 106.

In response to a determination that the initial version of source code106 is not used (no branch; decision step 216), code overlay creationprogram 200 loops to step 206. In one embodiment, code overlay creationprogram 200 determines a new offset/index value (at step 206) for thecode overlay based on the modified version of source code 106. Inanother embodiment, code overlay creation program 200 determines thatthe offset/index value of the code overlay did not change. In someembodiments, code overlay creation program 200 updates the informationassociating the code overlay with the modified version of source code106. For example, the modified version of source code 106 may have adifferent file name or a different directory location.

In decision step 216, in response to a determination that the initialversion of source code 106 is used (yes branch; decision step 216), codeoverlay creation program 200 stores the code overlay and the informationassociated with the code overlay (step 212).

Referring to decision step 210, in response to a determination thatsource code 106 was not modified (no branch; decision step 210), codeoverlay creation program 200 stores the code overlay and informationassociated with the code overlay.

In step 212, code overlay creation program 200 stores the code overlayand information associated with the code overlay. In some embodiments,information related to a code overlay is stored in at least one of alist and a table. For example, Table 3 depicts a list of example codeoverlays and associated offsets for a modified version (e.g., v02) ofsource code file Name.html utilizing test and debug configuration (e.g.,scheme01). In this example, code overlay creation program 200determined, in step 206, that multiple changes occurred between sourcecode files Name.v02.html and Name.v01.html. In Table 3, code overlaycreation program 200 adjusts the offset values associated with codeoverlays by signifying the bias value in parentheses (e.g., (+5)). Codeoverlay creation program 200 determines that no modifications thateffected the line numbering of source code Name.v02.html occurred priorto code line 15. Code overlay creation program 200 also determines thata first modification to source code Name.v02.html occurred after codeline 15 and before code line 25, and the first modification added fivelines of code. Code overlay creation program 200 determines that asecond modification to source code Name.v02.html occurred after codeline 30 and before code line 40 and that the second modification removed(e.g., deleted) two lines of code. Code overlay creation program 200determines that a third modification to source code Name.v02.htmloccurred after code line 40 and before code line 60, and the thirdmodification added three lines of code.

TABLE 3 Example code overlay list with offsets associated with testingand debug configuration file: Name.v02.scheme01.html d:\IDE\sourcecode\Name.v02.html Name Code Code Code Overlay.001.txt Overlay.002.txtOverlay.003.txt Directory location d:\libraries\ d:\libraries\d:\libraries\ overlays overlays overlays Offset value Offset valueOffset value Instance (bias values) (bias values) (bias values) 1  5(+0) 15 (+0) 25 (+5) 2 30 (+5) — 40 (+5) (−2) 3 — — 60 (+5) (−2) (+3)

In other embodiments, the information is embedded within the codeoverlay, such as flags, variables, delimiters, and syntax structures(e.g., commands) that prevent the incorporation of information withinthe composite code. Examples of the effect of syntax structures include:defining an insertion point; generating pseudo-code; defining a numberof repetitions of the inserted code; identifying comments; andperforming chain/combined actions. In some scenarios, code overlaycreation program 200 saves an offset/index value associated with eachline of text that is subsequently utilized to generate composite code107. In other scenarios, code overlay creation program 200 summarizesthe content of a code overlay. In some instances, code overlay creationprogram 200 identifies common lines of text and determines an absoluteoffset/index value for each occurrence of a line of text. In otherinstances, code overlay creation program 200 utilizes a combination ofabsolute offset/index values and relative values (e.g., the number oflines of code to skip prior to the next instance of the code overlay).

In another embodiment, code overlay creation program 200 identifies thecode overlay and information associated with the code overlay via a Diffutility and stores the results. In one scenario, code overlays arecreated and saved in a sequential manner and code overlay creationprogram 200 creates multiple Diff files (not shown). In some scenarios,code overlay creation program 200 creates Diff files that refer back tothe source code, and the Diff files may be used to undo one code overlayindependent of other code overlays. In other scenarios, code overlaycreation program 200 creates subsequent Diff files based on thecumulative changes to the source code associated with previous codeoverlays that appear in the edited version of the code. Subsequently, insome embodiments, code overlay integration program 300 utilizes a Patchutility to apply the code overlays and/or the files, created by a Diffutility, to source code 106 to generate composite code 107. In someinstances, utilizing a Diff utility and a Patch utility may limit thecapabilities of code overlays.

FIG. 3 is a flowchart depicting operational steps of code overlayintegration program 300. Code overlay integration program 300respectively monitors client device 120 and activities of the user ofclient device 120 and client device 130 and activities of the user ofclient device 130. Code overlay integration program 300 may executeconcurrently with software editing program 108 and code overlay creationprogram 200. In some embodiments, code overlay integration program 300includes display capabilities that enable a user to monitor theapplication of one or more code overlays to source code 106, which inturn generates composite code 107. In other embodiments, code overlayintegration program 300 utilizes the display capabilities of softwareediting program 108 to apply and monitor one or more code overlays tosource code 106, which in turn generates composite code 107.

In step 302, code overlay integration program 300 receives source code106 or a composite code configuration. In one embodiment, code overlayintegration program 300 receives source code 106 as a function of a userof client device 120 creating a code overlay via software editingprogram 108. In another embodiment, code overlay integration program 300receives source code 106 based on debug activity initiated by anintegrated development environment (IDE). In some embodiments, codeoverlay integration program 300 determines the file attributes of thereceived version of source code 106 for subsequent detection ofmodifications to source code 106. In a different embodiment, codeoverlay integration program 300 receives a composite code configuration.For example, rather than creating an original testing/debuggingconfiguration, a user of client device 130 selects and receives acomposite code configuration created and stored by the user of clientdevice 120. The user of client device 130 subsequently modifies, via UI132, the received composite code configuration to facilitate the testingand debug activity that is the responsibility of the user of clientdevice 130.

In step 304, code overlay integration program 300 receives a codeoverlay to apply to source code 106. In one embodiment, code overlayintegration program 300 receives a code overlay as part of theactivities of a user of client device 120 creating a code overlay byexecuting software editing program 108. In another embodiment, codeoverlay integration program 300 receives a code overlay based on atleast one of a file and table previously linked to source code 106 aspart of a software development process.

In step 306, code overlay integration program 300 applies a code overlayto source code 106 to generate composite code 107. In some embodiments,code overlay integration program 300 enables a user to differentiatecode overlays from source code. For example, composite code 107 isdisplayed in one column where source code is displayed as one colortext, code overlays are displayed as one or more different colors, anddeleted text may be displayed as indented without code line values anddepicted by a strikethrough text font. In another example, code overlayintegration program 300 displays composite code 107 in two columns,where the left column depicts source code 106 with some types ofmodifications identified and spaces added signifying the code linesadded by a code overlay, and the right column depicts the one or morecode overlays. In one embodiment, code overlay integration program 300generates composite code 107 by applying one or more code overlays tosource code 106 at one or more dictated locations, and code overlays mayperform one or more modifications to source code 106. In thisembodiment, the one or more modifications that may occur as the resultof code overlay integration program 300 applying one or more codeoverlays include: adding one or more lines of computer instructions;adding one or more lines of comments; removing one or more lines ofcomputer instructions; and removing one or more lines of comments. Insome embodiments, code overlay integration program 300 applies commands(e.g., delete one or more lines of computer instruction, substitute oneor more lines of computer instructions, etc.) within a code overlayprior to inserting the computer instruction comprising the code overlay.In another embodiment, code overlay integration program 300 preservesthe one or more removed lines of computer instructions of source code106. In one scenario, code overlay integration program 300 leaves theone or more lines of computer instruction within source code 106 ascomment lines. In some instances, code overlay integration program 300creates a code overlay that contains instructions to revert the commentsto computer instructions. In another scenario, code overlay integrationprogram 300 converts the one or more removed lines of computerinstructions to a code overlay. In another embodiment, code overlayintegration program 300 does not preserve the one or more removed (e.g.,deleted) lines of computer instructions and comments.

Additionally, code overlay integration program 300 tracks the numberingof source code 106 as one or more code overlays are applied to sourcecode 106. In one embodiment, code overlay integration program 300applies the dictated one or more code overlays in a parallel process andupdates the numbering of the lines of code within composite code 107subsequent to the application of the code overlays. In anotherembodiment, code overlay integration program 300 applies two or morecode overlays in a serial process (e.g., one at a time). Code overlayintegration program 300 tracks updates to the numbering of compositecode 107 after each code overlay is applied. Code overlay integrationprogram 300 tracks the changes in the numbering associated withcomposite code 107 and applies the changes to the offset/index values ofsubsequent applications of code overlays.

In further embodiments, code overlay integration program 300 may applyactions dictated by syntax within a code overlay at specified locationswithin source code 106. For example, a code overlay may dictate thatcode lines 5, 25, and 40 of source code 106 are commented out and areinserted for code lines 5, 25, and 40, and the debug code of the codeoverlay is inserted at code line 60 (e.g., offset/index value 60).

In a different embodiment, code overlay integration program 300 mayapply actions dictated by a code overlay at locations within sourcecode. For example, a code overlay may dictate that code lines 5, 25, and40 of source code 106 (import util.list) are deleted. In this example,code overlay integration program 300 has reduced the length of sourcecode 106 by three lines of computer instructions. In response to thereduction in the number of lines of comprising source code 106, codeoverlay integration program 300 renumbers composite code and adjusts theoffset location for debug code of the code overlay. For example, codeline 60 becomes program line 57.

In decision step 308, code overlay integration program 300 determineswhether one or more additional code overlays are applied to source code106. In some embodiments, code overlay integration program 300determines that additional code overlays are applied to source code 106based on automated input (e.g., a script, a table, etc.). In otherembodiments, code overlay integration program 300 determines thatadditional code overlays are applied to source code 106 based on inputfrom a user (e.g., a user of client device 130).

In response to determining that additional code overlays are applied tothe source code (yes branch; decision step 308), code overlayintegration program 300 optionally updates one or more code overlays(step 320). In some embodiments, the offset value that determines thelocation at which a code overlay applies to source code 106 is definedwithin the code overlay. If code overlay integration program 300determines that another instance of the code overlay occurs at a secondlocation associated with source code 106, then code overlay integrationprogram 300 updates the code overlay by defining a second offset valuewithin the code overlay. Subsequently, code overlay integration program300 loops to step 304.

In response to determining that additional code overlays are not applied(no branch; decision step 308), code overlay integration program 300detects whether one or more modifications occur to source code 106(decision step 310). In one embodiment, code overlay integration program300 compares the file attributes (e.g., file size, time stamp, etc.) ofsource code 106 stored in file storage 104 to the previously determinedfile attributes of the received version of source code 106 (step 302) todetermine whether source code 106 is modified. In another embodiment,code overlay integration program 300 respectively compares the fileattributes of instances of source code 106 in file storage 124, onclient device 120, in file storage 134, on client device 130, and infile storage 104 on server 102 to determine whether one of the instancesof source code 106 is modified.

In decision step 310, in response to detecting that one or moremodifications occurred to source code 106 (yes branch; decision step310), code overlay integration program 300 resolves the conflictassociated with the one or more detected modifications to source code106 (step 322).

In step 322, code overlay integration program 300 generates compositecode 107. In one embodiment, code overlay integration program 300resolves the conflict between versions (e.g., copies of source code 106that contain different modifications) of source code 106 and uses theinitial version of source code 106. In one scenario, code overlayintegration program 300 resolves the conflict by determining that codeoverlay creation program 200 and code overlay integration program 300are operating on the same version of source code 106. For example, auser of client device 120 and a user of client device 130 may benon-collaboratively debugging respectively developed portions of sourcecode 106 where both users modify source code 106 while creating codeoverlays for their respective portions of source code 106. Code overlayintegration program 300 can determine that each user is executingdifferent instances of code overlay creation program 200 and codeoverlay integration program 300 and determine that such modifications tosource code 106 do not cause a conflict. In another scenario, codeoverlay integration program 300 can determine that a user of clientdevice 120 and client device 130 are collaboratively debugging portionsof source code 106 that were respectively developed and determine thatno conflict occurs because the modification of portions of source code106 of one user do not occur at the locations of code overlays of theother user. In some scenarios, code overlay integration program 300resolves the conflict between versions of source code 106 by analyzingat least one of one or more user preferences and one or more softwaredevelopment preferences. For example, code overlay integration program300 determines that a software development preference dictates that auser download a copy of source code 106 to local storage (e.g., filestorage 124 on client device 120) and execute code overlay creationprogram 200 and code overlay integration program 300 remotely via UI122.

Referring to step 320, in some embodiments, code overlay integrationprogram 300 updates one or more code overlays based on the results ofstep 322. For example, if code overlay integration program 300determines that the modified version of source code 106 is used, thencode overlay integration program 300 updates the offset values of one ormore code overlays affected by the updates to source code 106.

In another embodiment, code overlay integration program 300 determinesthat the modified version of source code 106 is used to generate a newcomposite code 107. In addition, code overlay integration program 300detects that the modifications deleted one or more portions of sourcecode 106 that existed prior to the modifications and those deletedportions of source code 106 contained locations where one or more codeoverlays were applied. In one scenario, code overlay integration program300 removes the code overlays and offset values (e.g., locationinformation) associated with the code overlays in the deleted portionsof source code 106 from the subsequent generation of composite code 107.In another scenario, code overlay integration program 300 contacts auser of client device 120 via network 110 and UI 122 and awaits adisposition for the one or more affected code overlays.

Referring to decision step 310, if code overlay integration program 300does not detect modifications to source code 106 (no branch; decisionstep 310), then code overlay integration program 300 displays and/orexecutes composite code 107 (step 314). In one embodiment, code overlayintegration program 300 includes display capabilities that enable a userto view composite code 107. In another embodiment, code overlayintegration program 300 utilizes the display capabilities of softwareediting program 108 to display composite code 107. In some embodiments,code overlay integration program 300 differentiates the display of oneor more code overlays from code lines of source code 106.

In addition, code overlay integration program 300 may execute compositecode 107. In some embodiments, code overlay integration program 300interacts with an IDE and presents some or all of the interactions tothe user of client device 120 via UI 122. In one embodiment, codeoverlay integration program 300 executes composite code 107 for thepurpose of a user preforming at least one of debugging and testingcomposite code 107. In one scenario, code overlay integration program300 saves the results of the execution of composite code 107 in one ormore separate files for off-line analysis. For example, the one or moreresultant files of testing and/or debug activity may include errorcodes, error messages, variables, execution paths, lists, databasetables, etc. In another scenario, testing and debugging information isaccessible via code overlay integration program 300. In some instances,code overlay integration program 300 includes or accesses variousdebugging capabilities (e.g., stop on error, execute block, executeline, etc.). In another embodiment, code overlay integration program 300enables multiple users (e.g., a user of client device 120 and a user ofclient device 130) to test and debug composite code 107. In onescenario, code overlay integration program 300 executes one instance ofcomposite code 107, and multiple users review and respond to that oneinstance. In another scenario, code overlay integration program 300creates multiple instances of composite code 107, which the multipleusers may view via the execution of composite code 107 on server 102, onclient device 120, on client device 130, or any combination thereof.

In step 316, code overlay integration program 300 optionally stores thecomposite code configuration prior to terminating. In one embodiment,code overlay integration program 300 stores composite code 107 as thecomposite code configuration (e.g., a file containing source code 106 asmodified by any code overlays and all associated code overlays and theirrespective locations.). In another embodiment, code overlay integrationprogram 300 produces a configuration (e.g., testing/debugging scheme)structured as a list, a table, or a combination thereof, which includesthe code overlays and their respective locations that a user applied tosource code 106 during this testing and debug cycle. Such lists and/ortables can include information, such as code overlay names, code overlaydirectory locations, source code file names and versions, source codefile locations, code overlay locations, results of executing compositecode 107, permission levels, authors (e.g., programmers) of compositecode 107, editors (e.g., programmers) of composite code 107, etc.

In another embodiment, code overlay integration program 300 receives anindication from a user of client device 130 that the testing anddebugging of source code 106 is complete. Additionally, code overlayintegration program 300 receives a list of instructions which mayindicate which code overlays to convert to source code, which codeoverlays to remove from composite code 107, which stored code overlaysthat are reincorporated within composite code 107, and the name,revision information, and a storage location for the source codegenerated by the instructions.

FIG. 4a is an illustrative example of a snippet of source code which issubsequently acted on by code overlays, in accordance with an embodimentof the present invention.

Item 400 represents a visual depiction of a snippet of source code.Source code snippet 400 is a portion of a version of source code 106,identified by file name scr_code001.cpp (item 401).

Column 402 depicts the line numbers of each line of code of source codefile scr_code001.cpp (item 401) within source code snippet 400.

Column 403 depicts lines of programming code of source code filescr_code001.cpp (item 401), depicted within source code snippet 400.

FIG. 4b is an illustrative example of the results of code overlay 005(item 420) and code overlay 006 (item 412) being applied to source code106 file name scr_code001.cpp (item 401) to generate composite codesnippet 411, in accordance with an embodiment of the present invention.In this illustrative example, code overlay 005 (item 420) is received(e.g., step 304) and is applied (e.g., step 306) to source code 106 filename scr_code001.cpp (item 401) to generate composite code snippet 411.A user indicates to code overlay integration program 300 that anadditional code overlay 006 (item 412) is applied (e.g., yes branch;decision step 308) to source code 106 file name scr_code001.cpp (item401). Code overlay 006 (item 412) is received and applied to generatecomposite code 107 file name comp code0001.cpp (item 410) depicted incomposite code snippet 411.

Code overlay 006 (item 412) depicts an illustrative example of a codeoverlay, in accordance with an embodiment of the present invention. Codeoverlay 006 (item 412) comprises comment line 413, delimiting line 414,and three lines of text (e.g., functional lines), which are furthercomprised of actors (e.g., output text) and actions (e.g., functions)(in columns 415 and 416). Comment line 413 describes the purpose of codeoverlay 006 (item 412). Code overlay 006 (item 412) deactivates a codemodule with comment block commands. For example, if column 415 containstwo hash symbols/pound signs (i.e., ##), then one or more actions occurbased on subsequent symbols and text. In some embodiments, additionalinstances of delimiting line 414 and comment line may include additionalinformation, such as meta-data, authorship of the code overlay, tags,version number, directory location, etc. In other embodiments, codeoverlays may utilize syntax symbols and conventions of other languages(e.g., HTML) when including functional text. For example, a code overlaymay include syntax, separated by an addition delimiting line, thatidentifies another programming language (e.g., HTML) whose syntax isutilized. The syntax of the code overlay may include a flag specifyingthe starting point for the use of other programming language and thestopping point for the use of the other programming language.

Column 416 depicts two types of actions. An at-sign (i.e., @) in column416 signifies that subsequent symbols and text are associated with oneor more line numbers (e.g., offset/index values) of source code (e.g.,scr_code001.cpp (item 401)). An isolated plus sign (i.e., +) in column416 signifies that the subsequent symbols and text are added to a sourcecode file (e.g., scr_code001.cpp (item 401)) at one or more locations.In some embodiments, functional syntax is utilized outside of column416. In this example, additional symbols and the associatedsyntax/function include, but are not limited to: a dollar sign (“$”)signifying a variable string (e.g., variable name: list of list); acomma (“,”) for separating functions, function inputs, syntax, text, anditems of a list; a tilde (“{tilde over ( )}”) for translating orextracting information within quotation marks; an ampersand (“&”) forapplying or incorporating an element; a plus sign followed by a number(e.g., “+1”) for adding/inserting a certain number of elements, lines,etc.; a minus sign followed by a number (e.g., “−1”) for deleting acertain number of elements, lines, etc.; and angled brackets enclosing anumber (e.g., “<9>”), for skipping/moving forward a certain number oflines of code.

For example, the syntax of functional line 417 decodes as: after (e.g.,@) code line 68 (e.g., offset/index value 68) of source code filescr_code001.cpp (item 401), add one line of information from next line(line 418) of code overlay 006 (item 412), skip nine lines relative tocode line 68 of source code file scr_code001.cpp (item 401), and add oneof information from next line (line 419) of code overlay 006 (item 412).

In code overlay 006 (item 412), line 418 decodes as an action occurs(e.g., ##), and the action is to add (+) callout 418 a (/*). Based onthe first set of values of the insert action of functional line 417,callout 418 a (/*) is added after line 68 of source code scr_code001.cpp(item 401). Next, line 419 decodes as an action occurs (e.g., ##) andthe action is to add (e.g., +) callout 419 a (/*). Based on the secondset of values of the insert action of functional line 417, nine lines ofcode are skipped, and one line of code from code overlay 006 (item 412)is added (e.g., callout 419 a (*/)). Callout 419 a (*/) is added afterline 78 of source code scr_code001.cpp (item 401). However, code overlay005 (item 420) is added prior to code overlay 006 (item 412), whichindicates an additional code overlay is applied (e.g., yes branch;decision step 308). Code overlay integration program 300 updates one ormore index/offset values associated with code overlay 006 (item 412)based on the effects that code overlay 005 (item 420) has on compositecode 107, as depicted by the increased code lines associated withcallout 424 (e.g., step 320).

In code overlay 005 (item 420), the purpose described in the commentline is that the code overlay inserts multiple debug print statements.Line 421 decodes as: define a variable string (e.g., $) named var_Listcomprised of variables i, itsLen, and itsTextSrch, which arerespectively located at code lines 56, 58, and 54 of source code snippet400.

In code overlay 005 (item 420), functional line 422 decodes as: aftercode line 68 of source code file scr_code001.cpp (item 401), add two ofinformation from next line (functional line 423) of code overlay 005(item 420). However, code overlay 005 (item 420) is applied to sourcecode file scr_code001.cpp (item 401) prior to code overlay 006 (item412). Code overlay integration program 300 tracks the numbering changeassociated with the application of code overlay 005 (item 420) whichadds two lines after code line 58. Code overlay integration program 300adds two to the offset/index value associated with code overlay 006(item 412).

In functional line 423 of code overlay 005 (item 420), the actionindicator (##) is followed by two plus signs (++). In some embodimentsof the present invention, the syntax of stringing two actions of thecharacter together signifies that the action is repeated. The number ofrepetitions is based on information contained in one or more previouscommands. In this example, functional line 422 indicated that two linesare added. In functional line 423 the tilde symbol ({tilde over ( )}) iscombined with an ampersand (&), and the ampersand is associated with astring variable, var_List. In an embodiment, such a combination ofsyntax may initiate the creation of temporary pseudo code. With respectto functional line 423, code overlay temporarily generates two lines oftext respectively incorporating the first variable of var_List (i) andthe second variable of var_List (itsLen). The lines of text generated byfunctional line 423 and applied to source code file scr_code001.cpp(item 401), based on functional line 422, are depicted in callout 424within composite code snippet 411.

Subsequently, code overlay integration program 300 applies of codeoverlay 006 (item 412). Based on the increase of two code linesresulting from applying code overlay 005 (item 420), callout 418 aappears in composite code snippet 411 at code line 71 (e.g., callout430). Similarly, callout 419 a of code overlay 006 (item 412) appears incomposite code snippet 411 at code line 81 (e.g., callout 431).

FIG. 4c is an illustrative example of creating code overlay 007 (item446 or item 450) based on modifications to a different instance ofsource code 106 file name scr_code001.cpp (item 440) to generatecommented source code snippet 441 utilizing software editing program108, in accordance with an embodiment of the present invention.

Commented source code snippet 441 depicts modification to a source codesnippet 400 of a different instance of source code 106 file namescr_code001.cpp (item 401). The modification comprises adding fourinstances of comment “//ConstructorCounter;”, as depicted in callouts442, 443, 444, and 445. In one embodiment, the comment of callout 442 ispasted into source code 106 file name scr_code001.cpp (item 401) aftercode line 50 and flagged as code overlay content (e.g., step 202). Codeoverlay creation program 200 subsequently determines an offset/index of50 for callout 442 (e.g., step 206). When the comment associated withcallout 443 is added and flagged as code overlay content (e.g., step208), then code overlay creation program 200 detects the modification(e.g., yes branch; decision step 210). Code overlay creation program 200determines that the initial source code is not used (no branch; decisionstep 216), and then code overlay creation program 200 determines anoffset/index value for the comment depicted by callout 443 (e.g., step206).

In commented source code snippet 441, the depicted code line for callout433 is 60, which represents an offset/index appears at 59. However, codeoverlay creation program 200 tracked the lines of content associatedwith callout 442 (one line) and biases the offset/index value for thecomment of callout 443 to 58. Similarly, when the comment depicted atcallout 444 is added to the code in commented source code snippet 441,code overlay creation program 200 determines that the code line numberis 69 and biases the code line number by 2 (one line for callout 442 andone line for callout 443). Finally, when the comment depicted at callout445 is added to the code in commented source code snippet 441, codeoverlay creation program 200 determines that the code line number is 79and biases the code line number by 3 (one line for callout 442, one linefor callout 443, and one line for callout 444). In some embodiments,code overlay creation program 200 identifies content that is repeated,and code overlay creation program 200 utilizes that information generatea summarized structure for a code overlay. For example, callouts 442,443, 444, and 445 are identical and are represented in a code overlay asdepicted at callout 449.

In one embodiment, the content of callouts 442, 443, 444, and 445 isadded in a serial manner, and code overlay creation program 200 createscode overlay 007 (item 446). In one scenario, code overlay creationprogram 200 summarizes the offset/index values (in step 206) utilizingsyntax referred to in the discussion of column 415 and column 416. Forexample, the four functional lines that comprise item 447 describe theoffset/index values for applying single lines of text to a source codefile. The syntax of the function lines decodes as: an action occurs(e.g., ##), after (e.g., @) an offset/index value, and add one line(e.g., +1). The offset/index values for callouts 442, 443, 444, and 445are 50, 58, 67, and 76 respectively.

In another embodiment, code overlay creation program 200 receives thecontent of callouts 442, 443, 444, and 445 in a parallel manner. Forexample, code lines 51, 60, 70, and 80 of commented source code snippet441 are highlighted in one operation and flagged as content for codeoverlay 007 (item 447). In this example, code overlay creation program200 may determine a code offset/index value for callout 442.Subsequently, code overlay creation program 200 determines that callouts442, 443, 444, and 445 are comprised of identical text and are one linelong. In step 206, code overlay creation program 200 utilizes theoffset/index value for callout 442 of 50 (code line number 51-one line)and determines relative offset/index values (e.g., skip lines) of 8, 9,and 9 for callouts 443, 444, and 445. Callout 448 depicts functionalsyntax comprised of an action indication (e.g., ##) and the action tooccur (e.g., ++). In some embodiments of the present invention, thesyntax of stringing two actions of the character together signifies thatthe action is repeated. In this instance, callout 449//ConstructorCounter; represents callouts 442, 443, 444, and 445depicted in commented source code snippet 441. Code overlay creationprogram 200 utilizes this information to produce the syntax depicted infunction line 451. In the above embodiments, code overlay creationprogram 200 generates code overlay 007 (item 446) and code overlay 007(item 450) which are different but functionally equivalent.

FIG. 5 depicts computer system 500, which is representative of server102, client device 120, and client device 130. Computer system 500 is anexample of a system that includes software and data 512. Computer system500 includes processor(s) 501, cache 503, memory 502, persistent storage505, communications unit 507, input/output (I/O) interface(s) 506, andcommunication fabric 504. Communication fabric 504 providescommunications between cache 503, memory 502, persistent storage 505,communications unit 507, and input/output (I/O) interface(s) 506.Communications fabric 504 can be implemented with any architecturedesigned for passing data and/or control information between processors(such as microprocessors, communications and network processors, etc.),system memory, peripheral devices, and any other hardware componentswithin a system. For example, communications fabric 504 can beimplemented with one or more buses or a crossbar switch.

Memory 502 and persistent storage 505 are computer readable storagemedia. In this embodiment, memory 502 includes random access memory(RAM). In general, memory 502 can include any suitable volatile ornon-volatile computer readable storage media. Cache 503 is a fast memorythat enhances the performance of processor(s) 501 by holding recentlyaccessed data, and data near recently accessed data, from memory 502.

Program instructions and data used to practice embodiments of thepresent invention may be stored in persistent storage 505 and in memory502 for execution by one or more of the respective processor(s) 501 viacache 503. In an embodiment, persistent storage 505 includes a magnetichard disk drive. Alternatively, or in addition to a magnetic hard diskdrive, persistent storage 505 can include a solid hard drive, asemiconductor storage device, a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM), a flash memory, or any othercomputer readable storage media that is capable of storing programinstructions or digital information.

The media used by persistent storage 505 may also be removable. Forexample, a removable hard drive may be used for persistent storage 505.Other examples include optical and magnetic disks, thumb drives, andsmart cards that are inserted into a drive for transfer onto anothercomputer readable storage medium that is also part of persistent storage505. Software and data 512 are stored in persistent storage 505 foraccess and/or execution by one or more of the respective processor(s)501 via cache 503 and one or more memories of memory 502. With respectto server 102, software and data 512 includes file storage 104, sourcecode 106, composite code 107, software editing program 108, code overlaycreation program 200, code overlay integration program 300, and variousprograms (not shown). With respect to client device 120, software anddata 512 includes user interface (UI) 122, file storage 124, and variousprograms (not shown). With respect to client device 130, software anddata 512 includes user interface (UI) 132, file storage 134, and variousprograms (not shown).

Communications unit 507, in these examples, provides for communicationswith other data processing systems or devices, including resources ofserver 102, client device 120, and client device 130. In these examples,communications unit 507 includes one or more network interface cards.Communications unit 507 may provide communications through the use ofeither or both physical and wireless communications links. Programinstructions and data used to practice embodiments of the presentinvention may be downloaded to persistent storage 505 throughcommunications unit 507.

I/O interface(s) 506 allows for input and output of data with otherdevices that may be connected to each computer system. For example, I/Ointerface(s) 506 may provide a connection to external device(s) 508,such as a keyboard, a keypad, a touch screen, and/or some other suitableinput device. External device(s) 508 can also include portable computerreadable storage media such as, for example, thumb drives, portableoptical or magnetic disks, and memory cards. Software and data used topractice embodiments of the present invention can be stored on suchportable computer readable storage media and can be loaded ontopersistent storage 505 via I/O interface(s) 506. I/O interface(s) 506also connect to display device 509.

Display device 509 provides a mechanism to display data to a user andmay be, for example, a computer monitor. Display device 509 can alsofunction as a touch screen, such as the display of a tablet computer ora smartphone.

The programs described herein are identified based upon the applicationfor which they are implemented in a specific embodiment of theinvention. However, it should be appreciated that any particular programnomenclature herein is used merely for convenience, and thus theinvention should not be limited to use solely in any specificapplication identified and/or implied by such nomenclature.

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Smalltalk, C++ or the like, andconventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

The descriptions of the various embodiments of the present inventionhave been presented for purposes of illustration, but are not intendedto be exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the invention.The terminology used herein was chosen to best explain the principles ofthe embodiment, the practical application or technical improvement overtechnologies found in the marketplace, or to enable others of ordinaryskill in the art to understand the embodiments disclosed herein.

1-20. (canceled)
 21. A system, comprising: at least one server havingone or more memories storing instructions and having one or moreprocessors configured to execute the instructions to cause the system toperform operations comprising: receiving a first file comprisingcomputer programming code; receiving a code overlay comprising one ormore modifications to be applied to the computer programming code of thefirst file; generating a second file comprising composite computerprogramming code, wherein the composite computer programming codecomprises the computer programming code of the first file modified bythe one or more modifications of the code overlay; executing thecomposite computer programming code of the second file; and storing thefirst file and the second file within the one or more memories.
 22. Thesystem of claim 21, wherein generating the second file comprising thecomposite computer programming code does not alter the computerprogramming code of the first file.
 23. The system of claim 21, whereinthe one or more modifications of the code overlay comprise addingadditional computer programming code, adding a comment, removing aportion of the computer programming code, removing a comment, or acombination thereof.
 24. The system of claim 21, wherein the codeoverlay comprises one or more modification locations associated with arespective modification of the one or more modifications, and computerprogramming code of the first file is modified by the one or moremodifications of the code overlay based on the modification location.25. The system of claim 21, wherein the one or more modifications of thecode overlay comprises removing a portion of the computer programmingcode, and the wherein the one or more operations comprise preserving theremoved portion of the computer programming code.
 26. The system ofclaim 25, wherein preserving the removed portion of the computerprogramming code comprises converting the removed portion to anadditional code overlay or to a comment in the composite computerprogramming code.
 27. A method, comprising: receiving, via one or moreprocessors, a first file comprising computer programming code;receiving, via the one or more processors, a code overlay comprising oneor more modifications to be applied to the computer programming code ofthe first file; generating, via the one or more processors, a secondfile comprising composite computer programming code, wherein thecomposite computer programming code comprises the computer programmingcode of the first file modified by the one or more modifications of thecode overlay; executing, via the one or more processors, the compositecomputer programming code of the second file; and storing, via the oneor more processors, the first file and the second file within a storagelocation.
 28. The method of claim 27, wherein generating the second filecomprising the composite computer programming code does not alter thecomputer programming code of the first file.
 29. The method of claim 27,comprising: determining, via the one or more processors, that thecomposite computer programming code is absent from a third filecomprising the computer programming code of the first file; andupdating, via the one or more processors, the computer programming codeof the third file based on the one or more modifications of the codeoverlay.
 30. The method of claim 27, comprising: determining, via theone or more processors, that a third file includes the computerprogramming code of the first file modified by one or more additionalmodifications of an additional code overlay; and updating, via the oneor more processors, the composite computer programming of the secondfile based on the one or more additional modifications of the additionalcode overlay.
 31. The method of claim 27, wherein the composite computerprogramming code comprises one or more modified portions of the computerprogramming code, and wherein the one or more modified portions areconfigured to output error information, output information specified bythe code overlay, pause the execution of the composite computerprogramming code, generate one or more handling exceptions, store data,or a combination thereof.
 32. The method of claim 27, wherein the codeoverlay is received via a user selection of the code overlay from adatabase of different types of code overlays.
 33. The method of claim27, comprising transmitting, via the one or more processors, thecomposite computer programming code of the second file for display on aclient device, wherein unmodified portions of the composite computerprogramming codes are displayed differently than the modified portionsof the composite computer code.
 34. The method of claim 27, wherein theone or more modifications of the code overlay comprises removing aportion of the computer programming code, and the method comprisespreserving, via the one or more processors, the removed portion of thecomputer programming code.
 35. The method of claim 34, whereinpreserving, via the one or more processors, the removed portion of thecomputer programming code comprises converting the removed portion to anadditional code overlay or to a comment in the composite computerprogramming code.
 36. The method of claim 27, comprising receiving, viathe one or more processors, an additional code overlay comprising one ormore additional modifications to be applied to the computer programmingcode of the first file, and wherein the composite computer programmingcode comprises the computer programming code of the first file modifiedby the one or more modifications of the code overlay and the one or moreadditional modifications of the additional code overlay in parallel. 37.A tangible, non-transitory, machine-readable medium, comprisinginstructions, that, when executed by one or more processors, cause theone or more processors to: receive a first file comprising computerprogramming code; receive a code overlay comprising one or moremodifications to be applied to the computer programming code of thefirst file; generate a second file comprising composite computerprogramming code, wherein the composite computer programming codecomprises the computer programming code of the first file modified bythe one or more modifications of the code overlay; execute the compositecomputer programming code of the second file; and store the first fileand the second file within a storage location.
 38. The system of claim37, wherein the instructions that, when executed by the one or moreprocessors cause the one or more processors to generate the second filecomprising the composite computer programming code does not alter thecomputer programming code of the first file.
 39. The system of claim 37,comprising machine-readable instructions that, when executed by the oneor more processors cause the one or more processors to: determine thatthe composite computer programming code is absent from a third filecomprising the computer programming code of the first file; and updatethe computer programming code of the third file based on the one or moremodifications of the code overlay.
 40. The system of claim 37,comprising machine-readable instructions that, when executed by the oneor more processors cause the one or more processors to: determine that athird file includes the computer programming code of the first filemodified by one or more additional modifications of an additional codeoverlay; and update the composite computer programming of the secondfile based on the one or more additional modifications of the additionalcode overlay.